Publishing PetroVR Projects
The current version of PetroVR supports two modes of publishing simulation results: posting them to a web page, and uploading them to a Dataflow database. These are available in the File Menu, and in the right-click menu on the Results Window. Scenarios results can also be uploaded to Dataflow.
Publish to the Web
Publish the current deterministic and probabilistic Plan results to a dedicated section in a website, to be viewed through a standard web browser even without PetroVR installed.
When you select this option, PetroVR asks for a project name that will be used in the published URL. This is by default the current project's name. Published projects are associated with the user who uploaded them, so that if a project with the same name already exists in the server you can only overwrite it if it was uploaded by you.
In projects published to the web it is possible to edit those Variables that have been tagged as Key Inputs in PetroVR, thus generating alternative cases from the base project. Note that these changes made on the published project do not affect the PetroVR project in your computer.
Publish to Dataflow
Publish the current deterministic Plan and Scenarios results to a Dataflow database. When you select this option, the Dataflow Export Wizard opens to guide you through the process.
In the first window you can check and modify the login details already entered in Options (Tools menu).
In the second window select the version of the database you wish to use. When you do so, the node hierarchy corresponding to that version appears below. There you can select a node in order to update it or to create a new node under it.
In the third window, choose between updating the selected node or creating a new one. To create a new node, enter a document name and select a type from among the types already associated with the selected document. Then 
select a mapping file (.csv) to match PetroVR results with Dataflow variables. You can use the 
button to edit the selected file in the Windows Notepad. See more on the mapping file below.
If you are exporting Scenarios, in this window you can choose between exporting each scenario as a separate document, or exporting all scenarios as scenarios of the same Dataflow document.
When you click Next to move on to the fourth window the mapping file is validated (only for exporting projects, not scenarios). Here you can choose to export the project to a single document, and/or to create a separate document for each Facility, Well Completion or Reservoir in the project. If more than one document type is available for the selected document, use the Document Type box to select the one to be used. Under Proration Policy choose whether costs other than those belonging to the PetroVR object will be disregarded (No proration), distributed evenly among objects (Equal parts) or based on production (Proportional to production).
In the last window you will see the list of variables listed in the mapping file. Those that could not be exported because the results in PetroVR did not exist are red and struck through.
The Dataflow Mapping File
The Dataflow mapping file matches PetroVR results with Dataflow variables. This is a .csv file with the simple format [PetroVR result];[Dataflow variable], e.g.:
PVR result; Dataflow variable
Production: Total: Gas: Rates; Production.Gas1.Rate
Production: Total: Oil: Rates; Production.Liquid1.Rate
The file can have the following sections:
[Project]
[Well Completion]
[Facility]
[Reservoir]
[Nodes]
Use the [Nodes] section to restrict the document types that can be created under the selected node.
In the [Well Completion], [Facility] and [Reservoir] sections use these labels as keywords between curly brackets to refer to the name of the object being processed, e.g,: Production: Well Completion: {Reservoir}: {Well Completion}: Gas: Rates; Production.Gas2.Rate